home *** CD-ROM | disk | FTP | other *** search
- Path: news.oryx.com!xcprhb
- From: xcprhb@oryx.com (Reg H. Beardsley)
- Newsgroups: alt.computer.consultants,comp.edu,comp.lang.basic.misc,comp.lang.c++,comp.lang.misc,comp.lang.pascal.borland,comp.lang.pascal.delphi.misc,comp.misc,comp.os.msdos.programmer,comp.os.os2.programmer.misc,comp.programming
- Subject: Re: Can we do programming without seeing the end user?
- Date: 26 Mar 1996 18:33:46 GMT
- Organization: Oryx Energy Company
- Distribution: world
- Message-ID: <4j9daa$b1h@lm1.oryx.com>
- References: <BYtKnOggyTxQ071yn@oslonett.no> <4ivp84$o0n@dfw-ixnews5.ix.netcom.com> <4j1a3b$ib4@nntp1.best.com> <4j1krt$lna@nuacht.iol.ie> <4j2qon$3f3@nntp1.best.com>
- NNTP-Posting-Host: tau.oryx.com
-
- I'd like to add a few comments on several sub-threads within this
- discussion. These are in no particular order:
-
- 1) The best software is written by a user who is also a programmer.
-
- Possible, but not especially likely. It depends entirely on the
- skill levels of the individual. Having worked on over 1 million
- lines of end user written code, I can reasonably assert that most
- such code is trash or worse. Trash you can throw away. 150,000
- lines of undocumented code that is essential to some business
- activity is an absolute nightmare.
-
- On the other hand. I could be considered proof of the assertion. I
- am by training a geologist and geophysicist. I write and maintain
- software used by geologists and geophysicists. I will somewhat
- immodestly claim to be pretty good at programming, though at this
- point I tend to plead diminished capacity in the science end of
- things.
-
- The real requirement is a willingness to take the need to understand
- both the problem domain and the solution domain seriously. Far too
- many people claim that only one of these is important.
-
- The statement IS true if the user/programmer takes programming seriously.
- Unfortunately this seems to seldom be the case.
-
- 2) Does the programmer have to have contact with the user.
-
- Someone needs to. It may or may not be the programmer. My observation
- is that it is typically the progammer simply because there is no analyst
- to do it. Hence the common title of programmer/analyst. A solution
- cannot be produced until the problem is understood. I personally
- think it would be better if an analyst talked to the user and then the
- programmer, however, I've never worked that way, so I can't be sure.
- I like programming and I like interaction with the users. I have noticed
- that when a single person is both analyst and programmer, that there
- is a strong temptation to cut short the analysis phase and start designing,
- or worse, coding.
-
- In my own work, I try to adhere to the rule that I write no code until
- I run out of excuses for not programming. Unfortunately, I'm not always
- rigorous in my adherence to this and then I get into trouble. When I
- follow it, things complete easily and often ahead of schedule.
-
- 3) Can I be left alone to program without being bothered by the users?
-
- Actually, I think the thread started with the search for justification
- for not haing to talk to users. Hopefully the answer will be yes.
-
- 100 years ago the majority of the population was engaged in agriculture
- in order to produce enough food for everyone to eat. It is my belief
- that in another 100 years the majority of the population will be engaged
- in software in order to keep the machines running so that everyone can
- eat.
-
- Have fun!
-
- --
-
- ------------------------------------------------------------------------
- I am solely responsible for the contents...
-
- Reginald H. Beardsley rhb@acm.org
-
- Consultant/Programmer
- ------------------------------------------------------------------------
-